Important: This configuration mode is supported from StarOS Release 12.1 onward.
rulebase_name is the Rulebase name configured at PCEF and must be an alphanumeric string of 1 through 63 characters.
Following command associates the PCC-Rulebase named pcc_rulebase1 for PCC-Profile instance on IPCF node.
default-rulebase-name pcc_rulebase1
[no] eval-priority priority_value timedef timedef_name [condition-group cond_grp_name] action-set actionset_name
no removes the last evaluation priority action-set.
priority_value must be an integer from 1 through 1023.
timedef timedef_name
Specifies a pre-configured time definition in PCC-Timedef Configuration mode and to be set for evaluation priority in a PCC-Service-Profile instance.
timedef_name is a pre-configured PCC-Timedef and must be an alphanumerical string of 1 through 63 characters.
condition-group cond_grp_name
cond_grp_name is a pre-configured PCC-Condition-Group and must be an alphanumerical string of 1 through 63 characters.
Important: An special PCC-Condition-Group “none” can be used to set the default PCC-Condition-Group for any-match typically used for a default condition for a session which does not match any of the conditions specified with higher evaluation priority.action-set actionset_name
actionset_name is a pre-configured PCC-Action-Set and must be an alphanumerical string of 1 through 63 characters.
Additionally timedef is used to accept the Timedefs to support the time-of-day-based procedures to trigger an evaluation priority. The action is triggered only when the time of session lies in the time span defined in specific PCC-Timedef timedef_name.
Default eval-priority has the lowest priority in the PCC-Service-Profile and as default eval-priority does not have any PCC-Condition-Group associated with it, all the actions in the action-set always be applied.
Following command sets the evaluation priority value as 1 for PCC-Condition-Group cond_1 along with PCC-Action-Set act_cond1 for PCC-Service-Profile instance on IPCF node:
Following command sets the evaluation priority value as 2 for PCC-Condition-Group none for any-match typically used for a default condition for a session which does not match any of the conditions specified with higher evaluation priority.along with PCC-Action-Set act_cond1 for PCC-Service-Profile instance on IPCF node:
svc_tag must be an alphanumerical string of 1 through 63 characters.
rule-name rule_name
Specifies a pre-defined PCC-Rulename on PCEF to be used with PCC-Service Tag svc_tag in a PCC-Service-Profile instance.
rule_name is a pre-defined PCC-Rulename on PCEF and must be an alphanumerical string of 1 through 63 characters.
rulebase-name rulebase_name
Specifies a pre-defined PCC-Rulebase name pre-defined on PCEF to be used with PCC-Service Tag svc_tag in a PCC-Service-Profile instance.
rulebase_name is a pre-defined PCC-Rulebase name on PCEF and must be an alphanumerical string of 1 through 63 characters.
Following command sets the PCC-Service Tag named Rule1 for PCC-Rulebase named pcc_rulebase1 for PCC-Service-Profile instance on IPCF node:
Following command sets the PCC-Service Tag named Rule11 for PCC-Rulename pcc_rule1 for PCC-Service-Profile instance on IPCF node:
The usage_mon_name must be an alphanumerical string from 1 through 63 characters.
Warning: If this keyword option is used with no usage-monitor usage_mon_name command, the PCC-Usage-Monitor instance named usage_mon_name is deleted with all configured parameters without prompting any warning or confirmation.The commands configured in this mode are defined in the PCC-Usage-Monitor Configuration Mode Commands chapter of Command Line Interface Reference.
Caution: This is a critical configuration. The PCC-Usage-Monitor for volume usage can not be configured without this configuration. Any change to this configuration would lead to removing or disabling configuration parameters defined here.Following command configures the PCC-Usage-Monitor named pcc_usage1 to track the usage of service with in a PCC-Service-Profile instance.
usage-monitor pcc_usage1
[default] unknown-services-treatment {not-allowed | qos-profile qos_prof_name precedence from start_preced to end_preced order {ascending | descending}}
Sets the configured PCC-Service for handling of unknown services at IPCF to default value of “Not allowed” which is to be used in Subscriber profile in PCC-Service instance on IPCF node.
qos-profile qos_prof_name
qos_prof_name is a pre-defined PCC-QoS Profile and must be an alphanumerical string of 1 through 63 characters.
start_preced is an integer between 1 through 65535 and must be less than end_preced value where end_preced is an integer between 1 through 65535 and must be more than start_preced value
|
•
|
ascending sets the precedence setting in ascending order.
|
|
•
|
descending sets the precedence setting in descending order.
|
Whenever IPCF receives any request to authorize Packet Filters from PCEF, it does a lookup in data service list to find a match. If No service flow is found matching then the requested filters are treated as unknown service request and handled as per the mentioned configuration.
When unknown-service-treatment is set to not-allowed, then Packet Filters are rejected and no dynamic rule is installed. Otherwise, dynamic rule is created using the requested packet filters, data rates mentioned in the QoS profile name qos_prof_name and precedence value derived from the configured values.
|
•
|
If precedence limits are configured as 1000 to 2000 with order ascending then precedence of subsequent dynamic rules will go from 1000 to 2000.
|
|
•
|
If precedence limits are configured as 1000 to 2000 with order descending then precedence of subsequent dynamic rules will go from 2000 to 1000.
|
